Method and apparatus for network slice configuration

ABSTRACT

The present disclosure relates to network slice configuration methods and apparatus. One example method includes determining, by a first network device, network slice configuration information, and sending, by the first network device, the network slice configuration information to a second network device, where the network slice configuration information instructs the second network device to perform network slice configuration based on the network slice configuration information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/274,827, filed on Feb. 13, 2019, now U.S. Pat. No. 10,959,160, whichis a continuation of International Application No. PCT/CN2017/097533,filed on Aug. 15, 2017. The International Application claims priority toChinese Patent Application No. 201610671376.4, filed on Aug. 15, 2016.All of the aforementioned patent applications are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

This application relates to the field of communications technologies,and in particular, to a method and apparatus for network sliceconfiguration.

BACKGROUND

A future fifth generation (5G) mobile communications network can supportmore diversified service types and user requirements. Dramatic upgradeis to be achieved in aspects including speed, capacity, security,reliability, availability, latency, energy consumption, and the like.Compared with an existing 4th generation mobile communications network,the 5G network needs to meet more requirements: Network traffic is togrow by thousands of times, a quantity of to-be-connected devices growsby at least a hundred times as compared with a current quantity ofto-be-connected devices, and some services require an extremely lowdelay. The 5G network provides a “network customization” service toaddress diversification of future services. A network architecture is tobecome more flexible, and an operator can flexibly combine keyperformance indicators (KPI) such as speed, capacity, coverage, andreliability, so that the network architecture can meet a requirement ineach specific use case.

In a conventional mobile communications system, a vertical architectureis used with ranging from physical resources to protocol support, tomeet a predictable KPI requirement. The vertical architecture isapplicable to a user network of a single service type. However, it isdifficult for the vertical architecture to perform adaptive adjustmentbased on a flexible user requirement and meet a requirement of a newtype of use case. Therefore, the 3rd Generation Partnership Project(3GPP) presents a concept of network slicing in a 5G networkarchitecture. Network slicing is a combination of logical networkfunctions to meet a communications service requirement in a specific usecase. In network slicing, a logical resource instead of a physicalresource is used, to help the operator provide a service-based networkarchitecture. In such a network service, a resource and a requirementare allocated and reallocated, scalability of an independent networkfunction module and flexible deployment of physical and virtualfunctions are allowed, a network resource is fully and efficientlyutilized, and a service performance requirement is met.

Much technological implementation about network slicing in 3GPP is stillunder discussion. Currently, only the concept of network slicing and apotential network slice architecture are provided, and there is still nodefinite solution for how to perceive a network slice configurationprocess on a radio access network (RAN) side.

SUMMARY

Embodiments of this application provide a network slice configurationmethod and apparatus, to perceive a network slice configuration processon a radio access network side.

According to a first aspect, an embodiment of this application providesa network slice configuration method, including:

determining, by a first network device, network slice configurationinformation; and

sending, by the first network device, the network slice configurationinformation to a second network device, to instruct the second networkdevice to perform network slice configuration based on the network sliceconfiguration information.

According to the method provided in this embodiment of this application,after determining the network slice configuration information, the firstnetwork device sends the network slice configuration information to thesecond network device, so that the second network device may perform thenetwork slice configuration based on the network slice configurationinformation. In this way, a network slice configuration process isperceived on a radio access network side.

Optionally, the first network device is a core-network network element,and the second network device is an access-network network element; and

the determining, by a first network device, network slice configurationinformation includes:

determining, by the first network device, the network sliceconfiguration information based on a received network sliceconfiguration message sent by a third network device, where

the third network device is an operation, administration, and managementnetwork element.

Optionally, the first network device is a core-network network element,and the second network device is an access-network network element; and

before the determining, by a first network device, network sliceconfiguration information, the method further includes:

receiving, by the first network device, a network slice configurationrequest message sent by the second network device, where the networkslice configuration request message is used to request the first networkdevice to send the network slice configuration information, the networkslice configuration request message is sent after the second networkdevice receives a request message sent by a fourth network device, andthe fourth network device is a terminal or a target core-network networkelement.

Optionally, the first network device is a core-network network elementor an operation, administration, and management network element, and thesecond network device is an access-network network element; and

before the determining, by a first network device, network sliceconfiguration information, the method further includes:

receiving, by the first network device, capability information of thesecond network device that is sent by the second network device; and

the determining, by a first network device, network slice configurationinformation includes:

determining, by the first network device, the network sliceconfiguration information based on the capability information of thesecond network device.

Optionally, the capability information of the second network deviceincludes any one or more of the following information:

identification information of the second network device;

version information of the second network device;

antenna resource information of the second network device;

bandwidth resource information of the second network device;

load information of the second network device;

architecture resource information of the second network device; and

user information of the second network device.

Optionally, the first network device is a core-network network elementor an operation, administration, and management network element, and thesecond network device is an access-network network element; and

after the sending, by the first network device, the network sliceconfiguration information to a second network device, the method furtherincludes:

-   -   sending, by the first network device, a network slice management        message to the second network device, to instruct the second        network device to manage, based on the network slice management        message, the network slice configuration information in the        second network device.

Optionally, the network slice management message includes any one ormore of the following information:

a network slice activation command;

a network slice deactivation command;

a network slice enabling command;

a network slice disabling command;

network slice reconfiguration information; and

a network slice identifier.

Optionally, after the sending, by the first network device, the networkslice configuration information to a second network device, the methodfurther includes:

receiving, by the first network device, a response message sent by thesecond network device, where the response message is used to indicatethat the second network device refuses to accept the network sliceconfiguration information, and the response message includes a refusalreason.

Optionally, the network slice configuration information includes any oneor more of the following information:

network slice user information;

network slice service management information;

network slice attribute information; and

network slice resource control information.

Optionally, the network slice user information includes any one or moreof the following parameters:

network slice identification information;

mobile operator information; and

user information.

Optionally, the network slice service management information includesany one or more of the following parameters:

network slice identification information;

a quality of service QoS parameter of each terminal;

a QoS parameter of each network slice;

aggregate QoS information of N network slices to which M terminalsbelong, where M is a natural number and N is a natural number;

aggregate QoS information of K network slices, where K is a naturalnumber;

network slice priority information; and

congestion control information.

Optionally, the network slice attribute information includes any one ormore of the following parameters:

network slice identification information;

network slice routing information;

network slice service area information;

network slice target user information;

network slice coverage information;

network slice capacity and bandwidth information; and

network slice service time period information.

Optionally, the network slice resource control information includes anyone or more of the following parameters:

network slice identification information;

a network slice resource isolation requirement;

a network slice designation or preference requirement;

network slice topology information;

a network slice architecture requirement;

network slice resource configuration;

network slice protocol stack configuration;

network slice algorithm configuration; and

parameter configuration of each function module in a network slice.

Optionally, the aggregate QoS information of the N network slices towhich the M terminals belong includes any one or more of the followingparameters:

an aggregate throughput requirement of the N network slices to which theM terminals belong;

a maximum throughput limit of the N network slices to which the Mterminals belong; and

a minimum throughput limit of the N network slices to which the Mterminals belong.

Optionally, the aggregate QoS information of the K network slicesincludes at least one of the following information:

an aggregate throughput requirement of the K network slices;

a maximum throughput limit of the K network slices; or

a minimum throughput limit of the K network slices.

Optionally, the congestion control information includes any one or moreof the following parameters:

a network slice service overload instruction;

a network slice service load reduction instruction;

a network slice access level;

a network slice access control configuration category indication;

a network slice access restriction time; and

a network slice access restriction factor.

Optionally, the network slice routing information includes any one ormore of the following parameters:

a core network control plane entity identifier; and

a core network user plane entity identifier.

Optionally, the network slice resource isolation requirement includesany one or more of the following indications:

whether architecture sharing is allowed;

whether air interface resource sharing is allowed;

whether protocol stack resource sharing is allowed; and

whether algorithm resource sharing is allowed.

Optionally, the network slice designation or preference requirementincludes any one or more of the following parameters:

a designated or preferred frequency;

a designated or preferred frequency band;

a designated or preferred radio access technology;

designated or preferred high- and low-frequency collaboration; and

a designated or preferred quantity of required resources.

Optionally, the network slice topology information includes any one ormore of the following indications:

whether relaying is used;

whether coordinated multipoint communication is used; and

whether device-to-device communication is used.

Optionally, the network slice architecture requirement includes any oneor more of the following parameters:

a control plane anchor position; and

core-network and access-network network element function reconstruction.

Optionally, the network slice resource configuration includes any one ormore of the following parameters:

an air interface resource size;

air interface resource time and frequency domain positions;

a generated access preamble sequence; and

an access preamble format.

Optionally, the network slice algorithm configuration includes any oneor more of the following parameters:

a mobility management algorithm;

a bearer management algorithm;

a paging algorithm; and

a security algorithm.

According to a second aspect, an embodiment of this application providesa network slice configuration apparatus. The apparatus includes:

a processing unit, configured to determine network slice configurationinformation; and

a transceiver unit, configured to send the network slice configurationinformation to a second network device, to instruct the second networkdevice to perform network slice configuration based on the network sliceconfiguration information.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processing unit is specifically configured to:

determine the network slice configuration information based on areceived network slice configuration message sent by a third networkdevice, where

the third network device is an operation, administration, and managementnetwork element.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processing unit is further configured to:

receive a network slice configuration request message sent by the secondnetwork device, where the network slice configuration request message isused to request the apparatus to send the network slice configurationinformation, the network slice configuration request message is sentafter the second network device receives a request message sent by afourth network device, and the fourth network device is a terminal or atarget core-network network element.

Optionally, the apparatus is a core-network network element or anoperation, administration, and management network element, and thesecond network device is an access-network network element; and

the transceiver unit is further configured to:

receive capability information of the second network device that is sentby the second network device; and

the processing unit is specifically configured to:

determine the network slice configuration information based on thecapability information of the second network device.

Optionally, the capability information of the second network deviceincludes any one or more of the following information:

identification information of the second network device;

version information of the second network device;

antenna resource information of the second network device;

bandwidth resource information of the second network device;

load information of the second network device;

architecture resource information of the second network device; and userinformation of the second network device.

Optionally, the apparatus is a core-network network element or anoperation, administration, and management network element, and thesecond network device is an access-network network element; and

the transceiver unit is further configured to:

send a network slice management message to the second network device, toinstruct the second network device to manage, based on the network slicemanagement message, the network slice configuration information in thesecond network device.

According to a third aspect, an embodiment of this application providesa network slice configuration apparatus, which may perform any networkslice configuration method provided in the first aspect.

In a possible design, a structure of the network slice configurationapparatus includes a processor and a transceiver. The processor isconfigured to provide support for the network slice configurationapparatus to perform corresponding functions in the foregoing networkslice configuration method. The transceiver is coupled to the processor,to support communication between the network slice configurationapparatus and a second network device, and send information or aninstruction related to the foregoing network slice configuration methodto a terminal. The network slice configuration apparatus may furtherinclude a memory. The memory is configured to store a programinstruction and is coupled to the processor.

According to a fourth aspect, an embodiment of this application providesa network slice configuration method, including:

receiving, by a second network device, network slice configurationinformation sent by a first network device; and

performing, by the second network device, network slice configurationbased on the network slice configuration information.

According to the method provided in this embodiment of this application,after receiving the network slice configuration information, the secondnetwork device may perform the network slice configuration based on thenetwork slice configuration information. In this way, a network sliceconfiguration process is perceived on a radio access network side.

Optionally, the first network device is a core-network network element,and the second network device is an access-network network element; and

before the receiving, by a second network device, network sliceconfiguration information sent by a first network device, the methodfurther includes:

sending, by the second network device, a network slice configurationrequest message to the first network device, where the network sliceconfiguration request message is used to request the first networkdevice to send the network slice configuration information.

According to a fifth aspect, an embodiment of this application providesa network slice configuration apparatus. The apparatus includes:

a transceiver unit, configured to receive network slice configurationinformation sent by a first network device; and

a processing unit, configured to perform network slice configurationbased on the network slice configuration information.

Optionally, the first network device is a core-network network element,and the apparatus is an access-network network element; and

the transceiver unit is further configured to:

send a network slice configuration request message to the first networkdevice, where the network slice configuration request message is used torequest the first network device to send the network slice configurationinformation.

According to a sixth aspect, an embodiment of this application providesa network slice configuration apparatus, which may perform any networkslice configuration method provided in the second aspect.

In a possible design, a structure of the network slice configurationapparatus includes a processor and a transceiver. The processor isconfigured to provide support for the network slice configurationapparatus to perform corresponding functions in the foregoing networkslice configuration method. The transceiver is coupled to the processor,to support communication between the network slice configurationapparatus and a second network device, and send information or aninstruction related to the foregoing network slice configuration methodto a terminal. The network slice configuration apparatus may furtherinclude a memory. The memory is configured to store a programinstruction and is coupled to the processor.

According to a seventh aspect, an embodiment of this applicationprovides a computer storage medium. The computer storage medium isconfigured to store a computer software instruction used by the networkslice configuration apparatus provided in the second aspect, andincludes a program designed to implement the first aspect.

According to an eighth aspect, an embodiment of this applicationprovides a computer storage medium. The computer storage medium isconfigured to store a computer software instruction used by the networkslice configuration apparatus provided in the fourth aspect, andincludes a program designed to implement the third aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a possible 5G network architectureaccording to an embodiment of this application;

FIG. 2 is a schematic diagram of a system architecture according to anembodiment of this application;

FIG. 3 is a schematic flowchart of a network slice configuration methodaccording to an embodiment of this application;

FIG. 4 is a schematic flowchart of network slice configuration accordingto an embodiment of this application;

FIG. 5 is a schematic flowchart of network slice configuration accordingto an embodiment of this application;

FIG. 6 is a schematic flowchart of network slice configuration accordingto an embodiment of this application;

FIG. 7 is a schematic flowchart of network slice configuration accordingto an embodiment of this application;

FIG. 8 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application;

FIG. 9 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application;

FIG. 10 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application;and

FIG. 11 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

Key driving factors for implementing 5G network slicing are a softwaredefined network SDN (SDN) and network function virtualization (NFV). AnSDN technology subverts a network element form and decouples a networkfunction and hardware, thereby allowing a vertical system to besubdivided into programmable function modules to form a connectablehorizontal network architecture that is applicable to a flexibleextended service, and providing a network connection as a service basedon a service requirement by using the programmable function, to achievea purpose of “network as a service”. A mobile operator configures andmanages hundreds or thousands of network slices by configuring andorchestrating a series of network functions on a control platform in acore network (CN). The network slices relate to a series ofconfiguration and support for end-to-end network elements, includingdevices such as a user equipment (UE) and an access network (RAN). Thenetwork slices are created in the CN. In addition, on an access networkside, the core network and an operation, administration, and managementOAM (OAM) entity need to configure a network element on the accessnetwork side, to perform differentiated processing of services inend-to-end network slicing, thereby ensuring a corresponding servicelevel agreement (SLA) requirement and better supporting the end-to-endnetwork slicing.

Network slicing can implement network quality of service (QoS)isolation, flexible network management and control, and networkefficiency improvement. A network manager can break down end-to-end QoSrequirements to map the end-to-end QoS requirements to differentsub-network systems and forwarding devices, and create network slices atlow costs and a high speed without affecting an existing service. Aslice can open up some flexible programmable interfaces to a third-partyuser, so that the third-party user can design and develop a new networkservice based on the open interface and rapidly deploy the new networkservice. This brings considerable economic benefits to an operator, andimproves use efficiency of an existing network.

Currently, the 3GPP (3GPP) classifies typical 5G scenario use cases intothe following three types: an enhanced mobile broadband (eMBB) service,a massive machine-type connection (mMTC) service, and an ultra-reliableand low latency (URLLC) service. The eMBB means further improvingperformance such as user experience based on an existing mobilebroadband service scenario. The mMTC is mainly dedicated to anapplication scenario of the Internet of Things and is applicable to alarge-scale, low-power, low-cost, and deep-coverage Internet of Thingsterminal for providing a network access service. The URLLC is orientedto a service with strict requirements for data transmission reliabilityand latency, for example, the Internet of Vehicles, industrial control,and other scenarios. The three major scenarios include diversified anddifferentiated services, and not all of future use cases have relativelyhigh requirements for speed and coverage. Therefore, the 3GPP allows anoperator to construct a network slice by using an independent networkfunction set and parameter configuration, to meet requirements of aplurality of virtual operators. In addition, the 3GPP requires thatnetwork slices could be dynamically generated based on different marketscenarios.

FIG. 1 is a schematic diagram of a possible 5G network architecture. InFIG. 1 , a core network may be divided into a plurality of network sliceentities. Each network slice entity includes a set of network functions(NF) with specific functions. For example, in FIG. 1 , a network slice 1includes an NF 1, an NF 2, and an NF 3, a network slice 2 includes an NF4, an NF 5, and an NF 6, and a network slice 3 includes an NF 7 and anNF 8. A RAN is connected to the network slice entities by using a sliceselection and routing function (SSRF) module. After accessing the RAN, aterminal selects an appropriate network slice entity by using the SSRF,to access a data network, so that a customized service is provided byusing a specific NF and parameter configuration, thereby forming a 5Gend-to-end network slice architecture.

In the embodiments of this application, the terminal may be a wirelessterminal, for example, may be a mobile phone, a computer, a tabletcomputer, a personal digital assistant (PDA), a mobile Internet device(MID), a wearable device, an Internet Protocol (IP) phone, a networkprinter, or an electronic book reader (e-book reader).

The embodiments of this application may be applied to a mobilecommunications system such as a 5G communications system or a Long-TermEvolution (LTE) system. FIG. 2 is a schematic diagram of a systemarchitecture according to an embodiment of this application. The systemarchitecture shown in FIG. 2 includes an OAM network element, a CN, aRAN, and a terminal. A CN side includes a control plane (CP) entity anda user plane (UP) entity. A RAN side includes a slice controller, a userplane anchor, and a radio access node.

OAM network element: The OAM network element is mainly responsible forthree major categories of work based on an actual need of a mobileoperator: operation, administration, and maintenance. The operation ismainly routine work including analysis, prediction, planning, andconfiguration performed on a network and a service. The maintenance ismainly routine operation activities such as test box fault managementperformed on the network and the service. An administration function fora CN network slice is initiated by the OAM network element. The OAMnetwork element is responsible for interacting with a control planemodule corresponding to the CN and the RAN, to manage an end-to-endnetwork slice.

CP module on a CN side: may be a mobility management entity (MME), a CNmobility management anchor, and a CN network slice management entity,and works with a slice controller on the RAN side to perform functionssuch as connection management, session management, and mobilitymanagement for the end-to-end network slice.

Slice controller on the RAN side: is a CP plane module located on theRAN side, and mainly performs, based on network slice informationconfigured by the CP module or the OAM network element in the CN,functions such as RAN-side protocol function management, resourceallocation, topology management, inter-slice coordination andmanagement, RAN-side mobility management, system information, paging,and measurement. The slice controller may be used as an independentnetwork element, or deployed as a base station or an internal functionmodule of a RAN-side network element. In a cloud radio access network(cloud RAN, C-RAN) architecture, each protocol layer may be flexiblydefined. The slice controller may be further flexibly deployed on abaseband processing unit (baseband unit, BBU) or a remote radio unit(RRU), or deployed on a BBU and an RRU in a distributed manner. Theradio access network may include a relay scenario in which the slicecontroller may be flexibly deployed on a donor eNodeB (donor eNB, DeNB)or a relay node (RN).

Based on the foregoing description, FIG. 3 is a schematic flowchart of anetwork slice configuration method according to an embodiment of thisapplication.

Referring to FIG. 3 , the method includes the following steps:

Step 301. A first network device determines network slice configurationinformation.

Step 302. The first network device sends the network slice configurationinformation to a second network device, to instruct the second networkdevice to perform network slice configuration based on the network sliceconfiguration information.

Step 303. The second network device receives the network sliceconfiguration information sent by the first network device.

Step 304. The second network device performs the network sliceconfiguration based on the network slice configuration information.

In this embodiment of this application, the network slice configurationinformation includes any one or more of the following information:

network slice user information;

network slice service management information;

network slice attribute information; and

network slice resource control information.

Specifically, in this embodiment of this application, the network sliceuser information includes any one or more of the following parameters:network slice identification information, mobile operator information,and user information.

The network slice identification information includes but is not limitedto one or more pieces of identification information, and is used toindicate one network slice type or one specific network slice entity.

For example, the mobile operator information may be mobile operatoridentification information, such as a public land mobile network (PLMN),a mobile country code (MCC), and a mobile network code (MNC). Certainly,the foregoing are merely examples. Specific mobile operator informationmay be determined based on an actual situation.

For the user information, a user may be a tenant and a user of a networkslice, or may be a person or a legal person. The user information may bea unique identifier used to identify the user, for example, may be aninternational mobile subscriber identity (IMSI). Specific userinformation may be determined based on an actual situation.

In this embodiment of this application, the network slice servicemanagement information includes any one or more of the followingparameters:

a QoS parameter of each terminal, including but not limited toinformation about a throughput, a latency, and a packet loss rate ofeach terminal;

a QoS parameter of each network slice, including but not limited toinformation about a throughput, a delay, and a packet loss rate of eachnetwork slice;

aggregate QoS information of N network slices to which M terminalsbelong, including but not limited to an aggregate throughputrequirement, a maximum throughput limit, and a minimum throughput limitof the N network slices to which the M terminals belong, where M is anatural number, N is a natural number, the aggregate throughputrequirement of the N network slices to which the M terminals belong mayindicate that for a terminal, an aggregate throughput of the N networkslices to which the M terminals belong cannot be higher than or lowerthan the aggregate throughput requirement, and the maximum throughputlimit and the minimum throughput limit of the N network slices to whichthe M terminals belong may indicate that for a terminal, a maximumthroughput of one or more of the N network slices to which the Mterminals belong cannot be higher than the maximum throughput limit, anda minimum throughput thereof cannot be lower than the minimum throughputlimit;

aggregate QoS information of K network slices, including but not limitedto an aggregate throughput requirement, a maximum throughput limit, anda minimum throughput limit of the K network slices, where K is a naturalnumber, the aggregate throughput requirement of the K network slices mayindicate that for an access-network network element, an aggregatethroughput of the K network slices cannot be higher than or lower thanthe aggregate throughput requirement, and requirements for the maximumthroughput limit and the minimum throughput limit of the K networkslices may indicate that for an access-network network element, amaximum throughput of one or more of the K network slices cannot behigher than the maximum throughput limit, and a minimum throughputthereof cannot be lower than the minimum throughput limit;

network slice priority information, used when a plurality of networkslices conflict with each other when using resources or making adecision, where a network slice that preferentially uses a resource andother information is determined based on a network slice priority; and

congestion control information, including but not limited to: acongestion control parameter of an access-network network element, suchas a network slice service overload instruction or a network sliceservice load reduction instruction, where the network slice serviceoverload instruction is used to instruct the access-network networkelement to refuse a network connection setup request or a service setuprequest of a network slice corresponding to a network slice identifierin the congestion control information, and the network slice serviceload reduction instruction is used to instruct the access-networknetwork element to reduce a signaling load or a data service load of anetwork slice corresponding to a network slice identifier in thecongestion control information to an indicated percentage; an accesscontrol parameter of a terminal, such as a network slice access levelused by the terminal to determine, before accessing a network and basedon an access indication corresponding to the network slice access level,whether access to the network slice is allowed; a network slice accesscontrol configuration category indication, used by the terminal todetermine, when accessing a network slice and based on an access controlconfiguration category of the network slice, an access controlconfiguration parameter corresponding to the network slice. The accesscontrol configuration parameter may include a network slice accessrestriction time and a network slice access restriction factor. Beforeaccessing a network, the terminal determines, based on the accessrestriction time, a time that is required before the terminal is allowedto access the network. The network slice access restriction factor isused when the terminal determines a probability of successfullyaccessing the network slice. For example, the terminal generates arandom number, and determines a magnitude relationship between therandom number and the network slice access restriction factor. Theterminal is allowed to access the network only when the random number isgreater than or less than the access restriction factor.

In this embodiment of this application, the network slice attributeinformation includes any one or more of the following parameters:

network slice identification information, which includes but is notlimited to one or more pieces of identification information, and is usedto indicate one network slice type or one specific network slice entity;

network slice routing information, which includes but is not limited toa CN control plane entity identifier and a CN user plane entityidentifier, and is used in a RAN to route a service flow of a terminalto a CN control plane or a CN control plane entity that is designated bya corresponding network slice;

network slice service area information, specific to distribution of anavailable geographical area of a corresponding network slice;

network slice target user information, specific to a target user of acorresponding network slice;

network slice coverage information, specific to a coverage area of acorresponding network slice, where the network slice coverageinformation may be a cell list, a tracking area (TA) list, and the likeunder coverage of the network slice;

network slice capacity and bandwidth information, which is specific toguarantees of a capacity and bandwidth that are required by acorresponding network slice, and can indicate the capacity and thebandwidth that are required by the network slice; and

network slice use time period information, specific to a network slicewith a specific service time restriction, indicating that acorresponding network slice service is enabled for the network slice ina specified use time period.

In this embodiment of this application, the network slice resourcecontrol information includes any one or more of the followingparameters:

network slice identification information, which includes but is notlimited to one or more pieces of identification information, and is usedto indicate one network slice type or one specific network slice entity;

a network slice resource isolation requirement, including but notlimited to: whether architecture sharing is allowed, whether airinterface resource sharing is allowed, whether protocol stack resourcesharing is allowed, whether algorithm resource sharing is allowed, andthe like;

a network slice designation or preference requirement, including but notlimited to a designated or preferred frequency, frequency band, radioaccess technology (RAT), high- and low-frequency collaboration, quantityof required resources, and the like;

network slice topology information, including but not limited to:whether relaying is used, whether coordinated multipoint (CoMP)communication is used, and whether device-to-device (D2D) communicationis used;

a network slice architecture requirement, including but not limited to acontrol plane anchor position, CN and RAN network element functionreconstruction, and the like;

network slice configuration, including but not limited to an airinterface resource size, air interface resource time and frequencydomain positions, a generated access preamble sequence, an accesspreamble format, and the like;

network slice protocol stack configuration, including but not limited toprotocol configuration of a radio resource control (RRC) layer, a PacketData Convergence Protocol (PDCP) layer, a Radio Link Control (RLC)layer, a Medium Access Control (MAC) layer, a physical layer, and anon-access stratum (NAS) layer;

network slice algorithm configuration, including but not limited to amobility management algorithm, a bearer management algorithm, a pagingalgorithm, a security algorithm, and the like, and

parameter configuration of each function module in a network slice.

In this embodiment of this application, the first network device may bea core-network network element or an operation, administration, andmanagement network element, and the second network device is anaccess-network network element. The following provides detaileddescriptions separately.

In a possible scenario, the first network device may be a core-networknetwork element or an operation, administration, and management networkelement, and the second network device is an access-network networkelement.

In this scenario, optionally, before step 301, the second network devicemay send capability information of the second network device to thefirst network device, and the first network device receives thecapability information of the second network device that is sent by thesecond network device.

The capability information of the second network device includes any oneor more of the following information:

version information of the second network device, including but notlimited to information about a version used by or a version supported bythe second network device;

antenna resource information of the second network device, including butnot limited to an antenna resource available to the second networkdevice, such as a quantity of antennas and a quantity of antenna ports;

bandwidth resource information of the second network device, includingbut not limited to a bandwidth resource available to the second networkdevice, which includes but is not limited to a quantity of availableuplink resource blocks, a quantity of available downlink resourceblocks, a time domain position of an available resource block, afrequency domain position of an available resource block, and the like;

load information of the second network device, including but not limitedto a current load status of the second network device, which includesbut is not limited to a ratio of occupied uplink resources, a ratio ofoccupied downlink resources, a ratio of available uplink resources, aratio of available downlink resources, a quantity of connectedterminals, and the like;

architecture resource information of the second network device,including but not limited to available energy, power, storage, and thelike of the second network device; and

user information of the second network device, including but not limitedto a user category, a user identity, and the like of the second networkdevice.

In this case, in step 301, the first network device may determine thenetwork slice configuration information based on the capabilityinformation of the second network device, and the determined networkslice configuration information matches the capability information ofthe second network device. Specific determining may be performed basedon an actual situation. Details are not described herein.

In step 302, the first network device may send the determined networkslice configuration information to the second network device by using aconfiguration message, to be specific, send a configuration message thatincludes the network slice configuration information to the secondnetwork device. It should be noted that the first network device maysend the network slice configuration information during creation of anetwork slice, or may send the network slice configuration informationat any time after creation of a network slice. This is not limited inthis embodiment of this application.

In step 303, after receiving the network slice configurationinformation, the second network device may determine whether to acceptthe network slice configuration information, and return a responsemessage to the first network device. The response message returned bythe second network device may be a message indicating that the secondnetwork device refuses to accept the network slice configurationinformation, or may be a message indicating that the second networkdevice agrees to accept the network slice configuration information, ormay be another type of feedback message. This is not limited in thisembodiment of this application.

Optionally, when the response message returned by the second networkdevice is the message indicating that the second network device refusesto accept the network slice configuration information, a refusal reasonis further included, for example, QoS required by a network slice cannotbe met, or configuration required by a network slice is not compatiblewith the capability information of the second network device.

Finally, in step 304, the second network device stores the network sliceconfiguration information, and performs the network slice configurationbased on the network slice configuration information.

Optionally, after sending the network slice configuration information tothe second network device, the first network device may further send anetwork slice management message to the second network device, toinstruct the second network device to manage, based on the network slicemanagement message, the network slice configuration information in thesecond network device.

In this embodiment of this application, the network slice managementmessage includes any one or more of the following information:

a network slice activation command, used to activate network sliceconfiguration information configured in the second network device;

a network slice deactivation command, used to deactivate network sliceconfiguration information configured in the second network device;

a network slice enabling command, used to enable network sliceconfiguration information configured in the second network device;

a network slice disabling command, used to disable network sliceconfiguration information configured in the second network device;

network slice reconfiguration information, used to reconfigure networkslice configuration information configured in the second network device;and

a network slice identifier.

Optionally, after receiving the network slice management message, thesecond network device may determine whether to accept the network slicemanagement message, and return a network slice management responsemessage to the first network device. The network slice managementresponse message returned by the second network device may be refusingto accept the network slice management message, or may be agreeing toaccept the network slice management message, or may be another type offeedback message. This is not limited in this embodiment of thisapplication.

Optionally, when the network slice management response message returnedby the second network device is the message indicating that the secondnetwork device refuses to accept the network slice management message, arefusal reason is further included, for example. QoS required by anetwork slice cannot be met, or configuration required by a networkslice is not compatible with the capability information of the secondnetwork device.

In a possible scenario, the first network device is a core-networknetwork element, and the second network device is an access-networknetwork element.

In this scenario, optionally, before step 301, the first network devicemay receive a network slice configuration request message sent by thesecond network device. The network slice configuration request messageis used to request the first network device to send the network sliceconfiguration information. The network slice configuration requestmessage may be sent after the second network device receives a requestmessage sent by a fourth network device, and the request message is usedto instruct the second network device to perform the network sliceconfiguration. The fourth network device is a terminal or a targetcore-network network element. For example, in this case, the firstnetwork device may be an NF, and the fourth network device may be anSSRF.

Optionally, the network slice configuration request message sent by thesecond network device may be information such as network sliceidentification information or network slice type information.Correspondingly, the request message sent by the terminal may beinformation such as network slice identification information or networkslice type information.

In step 301, the first network device determines the network sliceconfiguration information based on a received network sliceconfiguration message sent by a third network device. The network sliceconfiguration message includes the network slice configurationinformation. The third network device is an operation, administration,and management network element.

Optionally, after receiving the network slice configuration message sentby the third network device, the first network device may return anetwork slice configuration response message to the third networkdevice. The network slice configuration response message returned by thefirst network device may be a message indicating that the first networkdevice refuses to accept the network slice configuration information, ormay be a message indicating that the first network device agrees toaccept the network slice configuration information, or may be anothertype of feedback message. This is not limited in this embodiment of thisapplication.

Optionally, when the network slice configuration response messagereturned by the first network device is the message indicating that thefirst network device refuses to accept the network slice configurationinformation, a refusal reason is further included, for example, QoSrequired by a network slice cannot be met, or configuration required bya network slice is not compatible with the capability information of thesecond network device.

In step 302, the first network device sends the determined network sliceconfiguration information to the second network device. For othercontent of this step, refer to the foregoing description. Details arenot described herein.

In step 303, after receiving the network slice configurationinformation, the second network device may further send a responsemessage to the first network device. For details, refer to the foregoingdescription. Details are not described herein.

Optionally, after receiving the network slice configuration information,the second network device may further send a network slice configurationnotification message that includes the network slice configurationinformation to the terminal, to instruct the terminal to store thenetwork slice configuration information.

The foregoing process is described below by using specific embodiments.

FIG. 4 is a schematic flowchart of network slice configuration accordingto an embodiment of this application.

In FIG. 4 , a first network device is a core-network network element oran operation, administration, and management network element, and asecond network device is an access-network network element.

Step 401: The second network device sends capability information of thesecond network device to the first network device.

Step 402. The first network device determines network sliceconfiguration information.

The first network device may determine the network slice configurationinformation based on the capability information of the second networkdevice.

Step 403: The first network device sends the determined network sliceconfiguration information to the second network device.

Step 404: The second network device returns a response message to thefirst network device.

The response message returned by the second network device may be amessage indicating that the second network device refuses to accept thenetwork slice configuration information, or may be a message indicatingthat the second network device agrees to accept the network sliceconfiguration information, or may be another type of feedback message.

Step 405. The second network device stores the network sliceconfiguration information.

Step 406. The first network device sends a network slice managementmessage to the second network device.

Step 407: The second network device returns a network slice managementresponse message to the first network device.

The network slice management response message returned by the secondnetwork device may be refusing to accept the network slice managementmessage, or may be agreeing to accept the network slice managementmessage, or may be another type of feedback message. This is not limitedin this embodiment of this application.

Step 408. The second network device stores the network slice managementmessage.

FIG. 5 is a schematic flowchart of network slice configuration accordingto an embodiment of this application.

In FIG. 5 , a first network device is a core-network network element, asecond network device is an access-network network element, and a thirdnetwork device is an operation, administration, and management networkelement.

Step 501. The third network device sends a network slice configurationmessage to the first network device.

The network slice configuration message includes network sliceconfiguration information.

Step 502: The first network device returns a network slice configurationresponse message to the third network device.

The network slice configuration response message may be a messageindicating that the first network device refuses to accept the networkslice configuration information, or may be a message indicating that thefirst network device agrees to accept the network slice configurationinformation, or may be another type of feedback message. This is notlimited in this embodiment of this application.

Step 503. The first network device determines the network sliceconfiguration information based on the received network sliceconfiguration message.

Step 504: The first network device sends the determined network sliceconfiguration information to the second network device.

Step 505: The second network device returns a response message to thefirst network device.

The response message returned by the second network device may be amessage indicating that the second network device refuses to accept thenetwork slice configuration information, or may be a message indicatingthat the second network device agrees to accept the network sliceconfiguration information, or may be another type of feedback message.

Step 506. The second network device stores the network sliceconfiguration information.

FIG. 6 is a schematic flowchart of network slice configuration accordingto an embodiment of this application.

In FIG. 6 , the first network device is a core-network network element,and the second network device is an access-network network element.

Step 601. A terminal sends a request message to the second networkdevice.

The request message is used to instruct the second network device toperform network slice configuration. The request message may includeinformation such as network slice identification information and networkslice type information.

Step 602. The second network device sends a network slice configurationrequest message to the first network device.

The network slice configuration request message may include theinformation such as the network slice identification information and thenetwork slice type information.

Step 603. The first network device sends a configuration message to thesecond network device, where the configuration message includes thenetwork slice configuration information.

Step 604: The second network device returns a response message to thefirst network device.

The response message returned by the second network device may be amessage indicating that the second network device refuses to accept thenetwork slice configuration information, or may be a message indicatingthat the second network device agrees to accept the network sliceconfiguration information, or may be another type of feedback message.

Step 605. The second network device stores the network sliceconfiguration information.

Step 606. The second network device sends a network slice configurationnotification message to the terminal. The network slice configurationnotification message includes the network slice configurationinformation. The terminal stores the network slice configurationinformation, such as network slice attribute information, network sliceservice management information, and network slice resource controlinformation. The terminal may perform protocol stack configuration,algorithm configuration, and the like based on the network sliceconfiguration information. The terminal may store access controlparameter information or the like of the terminal based on congestioncontrol information in the service management information.

FIG. 7 is a schematic flowchart of network slice configuration accordingto an embodiment of this application.

In FIG. 7 , a first network device is a core-network network element,for example, an NF; a second network device is an access-network networkelement; and a fourth network device is a target core-network networkelement, for example, an SSRF.

Step 701. The fourth network device sends a request message to thesecond network device.

The request message is used to instruct the second network device toperform network slice configuration. The request message may includeinformation such as network slice identification information and networkslice type information.

Step 702. The second network device sends a network slice configurationrequest message to the first network device.

The network slice configuration request message may include theinformation such as the network slice identification information and thenetwork slice type information.

Step 703. The first network device sends a configuration message to thesecond network device, where the configuration message includes thenetwork slice configuration information.

Step 704: The second network device returns a response message to thefirst network device.

The response message returned by the second network device may be amessage indicating that the second network device refuses to accept thenetwork slice configuration information, or may be a message indicatingthat the second network device agrees to accept the network sliceconfiguration information, or may be another type of feedback message.

Step 705. The second network device stores the network sliceconfiguration information.

Step 706. The second network device sends a network slice configurationnotification message to a terminal. The network slice configurationnotification message includes the network slice configurationinformation. The terminal stores the network slice configurationinformation, such as network slice attribute information, network sliceservice management information, and network slice resource controlinformation. The terminal may perform protocol stack configuration,algorithm configuration, and the like based on the network sliceconfiguration information. The terminal may store access controlparameter information or the like of the terminal based on congestioncontrol information in the service management information.

Based on a same technical concept, an embodiment of this applicationfurther provides a network slice configuration apparatus. The apparatuscan perform the foregoing method embodiments.

FIG. 8 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application.

Referring to FIG. 8 , the apparatus includes.

a processing unit 801, configured to determine network sliceconfiguration information; and

a transceiver unit 802, configured to send the network sliceconfiguration information to a second network device, to instruct thesecond network device to perform network slice configuration based onthe network slice configuration information.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processing unit 801 is specifically configured to:

determine the network slice configuration information based on areceived network slice configuration message sent by a third networkdevice, where

the third network device is an operation, administration, and managementnetwork element.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processing unit 801 is further configured to:

receive a network slice configuration request message sent by the secondnetwork device, where the network slice configuration request message isused to request the apparatus to send the network slice configurationinformation, the network slice configuration request message is sentafter the second network device receives a request message sent by afourth network device, and the fourth network device is a terminal or atarget core-network network element.

Optionally, the apparatus is a core-network network element or anoperation, administration, and management network element, and thesecond network device is an access-network network element; and

the transceiver unit 802 is further configured to:

receive capability information of the second network device that is sentby the second network device; and

the processing unit 801 is specifically configured to:

determine the network slice configuration information based on thecapability information of the second network device.

Optionally, the capability information of the second network deviceincludes any one or more of the following information:

identification information of the second network device;

version information of the second network device;

antenna resource information of the second network device;

bandwidth resource information of the second network device;

load information of the second network device;

architecture resource information of the second network device; and

user information of the second network device.

Optionally, the apparatus is a core-network network element or anoperation, administration, and management network element, and thesecond network device is an access-network network element; and

the transceiver unit 802 is further configured to:

send a network slice management message to the second network device, toinstruct the second network device to manage, based on the network slicemanagement message, the network slice configuration information in thesecond network device.

Optionally, the network slice management message includes any one ormore of the following information:

a network slice activation command;

a network slice deactivation command;

a network slice enabling command;

a network slice disabling command;

network slice reconfiguration information; and

a network slice identifier.

Optionally, the transceiver unit 802 is further configured to:

receive a response message sent by the second network device, where theresponse message is used to indicate that the second network devicerefuses to accept the network slice configuration information, and theresponse message includes a refusal reason.

Optionally, the network slice configuration information includes any oneor more of the following information:

network slice user information;

network slice service management information;

network slice attribute information; and

network slice resource control information.

Optionally, the network slice user information includes any one or moreof the following parameters:

network slice identification information;

mobile operator information; and

user information.

Optionally, the network slice service management information includesany one or more of the following parameters:

network slice identification information;

a quality of service QoS parameter of each terminal;

a QoS parameter of each network slice;

aggregate QoS information of N network slices to which M terminalsbelong, where M is a natural number and N is a natural number;

aggregate QoS information of K network slices, where K is a naturalnumber;

network slice priority information; and

congestion control information.

Optionally, the network slice attribute information includes any one ormore of the following parameters;

network slice identification information;

network slice routing information;

network slice service area information;

network slice target user information;

network slice coverage information;

network slice capacity and bandwidth information; and

network slice service time period information.

Optionally, the network slice resource control information includes anyone or more of the following parameters:

network slice identification information;

a network slice resource isolation requirement;

a network slice designation or preference requirement;

network slice topology information;

a network slice architecture requirement;

network slice resource configuration;

network slice protocol stack configuration;

network slice algorithm configuration; and

parameter configuration of each function module in a network slice.

Optionally, the aggregate QoS information of the N network slices towhich the M terminals belong includes any one or more of the followingparameters:

an aggregate throughput requirement of the N network slices to which theM terminals belong;

a maximum throughput limit of the N network slices to which the Mterminals belong; and

a minimum throughput limit of the N network slices to which the Mterminals belong.

Optionally, the aggregate QoS information of the K network slicesincludes at least one of the following information:

an aggregate throughput requirement of the K network slices;

a maximum throughput limit of the K network slices; or

a minimum throughput limit of the K network slices.

Optionally, the congestion control information includes any one or moreof the following parameters:

a network slice service overload instruction;

a network slice service load reduction instruction;

a network slice access level;

a network slice access control configuration category indication;

a network slice access restriction time; and

a network slice access restriction factor.

Optionally, the network slice routing information includes any one ormore of the following parameters;

a core network control plane entity identifier; and

a core network user plane entity identifier.

For other content about the apparatus shown in FIG. 8 , refer to thedescription related to FIG. 3 . Details are not described herein again.

Based on a same technical concept, an embodiment of this applicationfurther provides a network slice configuration apparatus. The apparatuscan perform the foregoing method embodiments.

FIG. 9 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application.

Referring to FIG. 9 , the apparatus includes a processor 901, a memory902, and a transceiver 903.

The memory 902 is configured to store a program instruction, and iscoupled to the processor 901. The transceiver 903 is coupled to theprocessor 901, to support communication between the network sliceconfiguration apparatus and a second network device.

The transceiver 903 may be a wired transceiver, a wireless transceiver,or a combination thereof. The wired transceiver may be, for example, anEthernet interface. The Ethernet interface may be an optical interface,an electrical interface, or a combination thereof. The wirelesstransceiver may be, for example, a wireless local area networktransceiver, a cellular network transceiver, or a combination thereof.The processor 901 may be a central processing unit (CPU), a networkprocessor (NP, or a combination of a CPU and an NP. The processor 901may further include a hardware chip. The hardware chip may be anapplication-specific integrated circuit (ASIC), a programmable logicdevice (PLD), or a combination thereof. The PLD may be a complexprogrammable logic device (CPLD), a field-programmable gate array(FPGA), generic array logic (GAL), or any combination thereof. Thememory 902 may include a volatile memory, for example, a random-accessmemory (RAM), or the memory 902 may include a non-volatile memory, forexample, a read-only memory (ROM), a flash memory, a hard disk drive(HDD), or a solid-state drive (SSD), or the memory 902 may include acombination of the foregoing types of memories.

The processor 901 is configured to determine network slice configurationinformation.

The transceiver 903 is configured to send the network sliceconfiguration information to the second network device, to instruct thesecond network device to perform network slice configuration based onthe network slice configuration information.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processor 901 is specifically configured to:

determine the network slice configuration information based on areceived network slice configuration message sent by a third networkdevice, where

the third network device is an operation, administration, and managementnetwork element.

Optionally, the apparatus is a core-network network element, and thesecond network device is an access-network network element; and

the processor 901 is further configured to:

receive a network slice configuration request message sent by the secondnetwork device, where the network slice configuration request message isused to request the apparatus to send the network slice configurationinformation, the network slice configuration request message is sentafter the second network device receives a request message sent by afourth network device, and the fourth network device is a terminal or atarget core-network network element.

For other content about the apparatus shown in FIG. 9 , refer to thedescription related to FIG. 3 . Details are not described herein again.

Based on a same technical concept, an embodiment of this applicationfurther provides a network slice configuration apparatus. The apparatuscan perform the foregoing method embodiments.

FIG. 10 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application.

Referring to FIG. 10 , the apparatus includes:

a transceiver unit 1001, configured to receive network sliceconfiguration information sent by a first network device; and

a processing unit 1002, configured to perform network sliceconfiguration based on the network slice configuration information.

Optionally, the first network device is a core-network network element,and the apparatus is an access-network network element; and

the transceiver unit 1001 is further configured to:

send a network slice configuration request message to the first networkdevice, where the network slice configuration request message is used torequest the first network device to send the network slice configurationinformation.

For other content about the apparatus shown in FIG. 10 , refer to thedescription related to FIG. 3 . Details are not described herein again.

Based on a same technical concept, an embodiment of this applicationfurther provides a network slice configuration apparatus. The apparatuscan perform the foregoing method embodiments.

FIG. 11 is a schematic structural diagram of a network sliceconfiguration apparatus according to an embodiment of this application.

Referring to FIG. 11 , the apparatus includes a processor 1101, a memory1102, and a transceiver 1103.

The memory 1102 is configured to store a program instruction, and iscoupled to the processor 1101. The transceiver 1103 is coupled to theprocessor 1101, to support communication between the network sliceconfiguration apparatus and a first network device.

The transceiver 1103 is configured to receive network sliceconfiguration information sent by the first network device.

The processor 1101 is configured to perform network slice configurationbased on the network slice configuration information.

Optionally, the first network device is a core-network network element,and the apparatus is an access-network network element; and

the transceiver 1103 is further configured to:

send a network slice configuration request message to the first networkdevice, where the network slice configuration request message is used torequest the first network device to send the network slice configurationinformation.

For other content about the apparatus shown in FIG. 11 , refer to thedescription related to FIG. 3 . Details are not described herein again.

FIG. 11 may further include a bus interface. The bus interface mayinclude any quantity of interconnected buses and bridges. Specifically,one or more processors represented by the processor and various memorycircuits represented by the memory are linked together. The businterface may further link various other circuits such as a peripheraldevice, a voltage regulator, and a power management circuit. These areall known in the art, and therefore are not further described in thisspecification. The bus interface provides an interface. The transceiverprovides a unit configured to communicate with various other devices ona transmission medium. The processor is responsible for managing a busarchitecture and general processing. The memory may store data to beused by the processor when the processor performs an operation.

This application further provides the following embodiments. Forexample:

Embodiment 1: A network slice configuration method includes:determining, by a first network device, network slice configurationinformation; and

sending, by the first network device, the network slice configurationinformation to a second network device, to instruct the second networkdevice to perform network slice configuration based on the network sliceconfiguration information.

Embodiment 2: Based on the method in Embodiment 1, the first networkdevice is a core network element, and the second network device is anaccess network element. The determining, by a first network device,network slice configuration information includes: determining, by thefirst network device, the network slice configuration information basedon a received network slice configuration message sent by a thirdnetwork device. The third network device is an operation,administration, and management network element.

Embodiment 3: Based on the method in Embodiment 1, the first networkdevice is a core network element, and the second network device is anaccess network element. Before the determining, by a first networkdevice, network slice configuration information, the method furtherincludes: receiving, by the first network device, a network sliceconfiguration request message sent by the second network device. Thenetwork slice configuration request message is used to request the firstnetwork device to send the network slice configuration information, thenetwork slice configuration request message is sent after the secondnetwork device receives a request message sent by a fourth networkdevice, and the fourth network device is a terminal or a target corenetwork element.

Embodiment 4: Based on the method in Embodiment 1, the first networkdevice is a core network element or an operation and management networkelement, and the second network device is an access network element.Before the determining, by a first network device, network sliceconfiguration information, the method further includes: receiving, bythe first network device, capability information of the second networkdevice that is sent by the second network device. The determining, by afirst network device, network slice configuration information includes:determining, by the first network device, the network sliceconfiguration information based on the capability information of thesecond network device.

Embodiment 5: Based on the method in Embodiment 4, the capabilityinformation of the second network device includes any one or more of thefollowing information:

identification information of the second network device;

version information of the second network device;

antenna resource information of the second network device;

bandwidth resource information of the second network device;

load information of the second network device;

architecture resource information of the second network device; and

user information of the second network device.

Embodiment 6: Based on the method in Embodiment 1, the first networkdevice is a core network element or an operation and management networkelement, and the second network device is an access network element.After the sending, by the first network device, the network sliceconfiguration information to a second network device, the method furtherincludes: sending, by the first network device, a network slicemanagement message to the second network device, to instruct the secondnetwork device to manage the network slice configuration information inthe second network device based on the network slice management message.

Embodiment 7: Based on the method in Embodiment 6, the network slicemanagement message includes any one or more of the followinginformation:

a network slice activation command;

a network slice deactivation command;

a network slice enabling command;

a network slice disabling command;

network slice reconfiguration information; and

a network slice identifier.

Embodiment 8: Based on the method in any one of Embodiments 1 to 7,after the sending, by the first network device, the network sliceconfiguration information to a second network device, the method furtherincludes: receiving, by the first network device, a response messagesent by the second network device. The response message is used toindicate that the second network device refuses to accept the networkslice configuration information, and the response message includes arefusal reason.

Embodiment 9: Based on the method in any one of Embodiments 1 to 8, thenetwork slice configuration information includes any one or more of thefollowing information:

network slice user information;

network slice service management information;

network slice attribute information; and

network slice resource control information.

Embodiment 10: Based on the method in Embodiment 9, the network sliceservice management information includes any one or more of the followingparameters:

network slice identification information;

a quality of service QoS parameter of each terminal;

a QoS parameter of each network slice;

aggregate QoS information of N network slices to which M terminalsbelong, where M is a natural number and N is a natural number;

aggregate QoS information of K network slices, where K is a naturalnumber;

network slice priority information; and

congestion control information.

Embodiment 11: Based on the method in Embodiment 9, the network sliceattribute information includes any one or more of the followingparameters:

network slice identification information;

network slice routing information;

network slice service area information;

network slice target user information;

network slice coverage information;

network slice capacity and bandwidth information; and

network slice service time period information.

Embodiment 12: Based on the method in Embodiment 10, the aggregate QoSinformation of the N network slices to which the M terminals belongincludes any one or more of the following parameters:

an aggregate throughput requirement of the N network slices to which theM terminals belong;

a maximum throughput limit of the N network slices to which the Mterminals belong; and

a minimum throughput limit of the N network slices to which the Mterminals belong.

Embodiment 13: Based on the method in Embodiment 10, the aggregate QoSinformation of the K network slices includes at least one of thefollowing information:

an aggregate throughput requirement of the K network slices:

a maximum throughput limit of the K network slices; or

a minimum throughput limit of the K network slices.

Embodiment 14: Based on the method in Embodiment 10, the congestioncontrol information includes any one or more of the followingparameters:

a network slice service overload instruction;

a network slice service load reduction instruction;

a network slice access level;

a network slice access control configuration category indication;

a network slice access restriction time; and

a network slice access restriction factor.

Embodiment 15: A network slice configuration apparatus includes aprocessor, a memory, and a transceiver, where the memory is configuredto store a program instruction, and is coupled to the processor, and thetransceiver is coupled to the processor, to support communicationbetween the network slice configuration apparatus and a second networkdevice; and

the processor is configured to perform the program instruction stored inthe memory, to provide support for the network slice configurationapparatus to perform the network slice configuration method according toany one of the foregoing embodiments 1 to 14.

This application is described with reference to the flowcharts and/orblock diagrams of the method, the device (system), and the computerprogram product according to the embodiments of this application. Itshould be understood that computer program instructions may be used toimplement each process and/or each block in the flowcharts and/or theblock diagrams and a combination of a process and/or a block in theflowcharts and/or the block diagrams. These computer programinstructions may be provided for a general-purpose computer, a dedicatedcomputer, an embedded processor, or a processor of any otherprogrammable data processing device to generate a machine, so that theinstructions executed by a computer or a processor of any otherprogrammable data processing device generate an apparatus forimplementing a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be stored in a computer readablememory that can instruct the computer or any other programmable dataprocessing device to work in a specific manner, so that the instructionsstored in the computer readable memory generate an artifact thatincludes an instruction apparatus. The instruction apparatus implementsa specific function in one or more processes in the flowcharts and/or inone or more blocks in the block diagrams.

These computer program instructions may be loaded onto a computer oranother programmable data processing device, so that a series ofoperations and steps are performed on the computer or the anotherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or the anotherprogrammable device provide steps for implementing a specific functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

Although some embodiments of this application have been described,persons skilled in the art can make changes and modifications to theseembodiments once they learn the basic inventive concept. Therefore, thefollowing claims are to be construed as to cover the preferredembodiments and all changes and modifications falling within the scopeof this application.

Obviously, persons skilled in the art can make various modifications andvariations to this application without departing from the scope of thisapplication. This application is intended to cover these modificationsand variations provided that these modifications and variations in thisapplication fall within the protection scope of the claims of thisapplication.

What is claimed is:
 1. A method for perceiving network sliceconfiguration, comprising: receiving network slice configurationinformation from a first network device, wherein: the network sliceconfiguration information comprises network slice service managementinformation, wherein the network slice service management informationcomprises aggregate quality of service (QoS) information of N networkslices to which M terminals belong, and wherein M is a natural numberand N is a natural number; and performing network slice configurationbased on the network slice configuration information.
 2. The methodaccording to claim 1, comprising: sending capability information of anaccess-network network element to the first network device, wherein thefirst network device determines the network slice configurationinformation based on the capability information of the access-networknetwork element, and wherein the capability information of theaccess-network network element comprises one or more of identificationinformation of the access-network network element, version informationof the access-network network element, antenna resource information ofthe access-network network element, bandwidth resource information ofthe access-network network element, load information of theaccess-network network element, architecture resource information of theaccess-network network element, and user information of theaccess-network network element.
 3. The method according to claim 1,wherein the aggregate QoS information of the N network slices to whichthe M terminals belong includes one or more of the following parameters:an aggregate throughput requirement of the N network slices to which theM terminals belong; a maximum throughput limit of the N network slicesto which the M terminals belong; or a minimum throughput limit of the Nnetwork slices to which the M terminals belong.
 4. A method forperceiving network slice configuration, comprising: sending networkslice configuration information to an access-network network element,wherein: the network slice configuration information comprises networkslice service management information, wherein the network slice servicemanagement information comprises aggregate quality of service (QoS)information of N network slices to which M terminals belong, and whereinM is a natural number and N is a natural number.
 5. The method accordingto claim 4, comprising: receiving capability information of theaccess-network network element from the access-network network element;and determining the network slice configuration information based on thecapability information of the access-network network element, whereinthe capability information of the access-network network elementcomprises one or more of identification information of theaccess-network network element, version information of theaccess-network network element, antenna resource information of theaccess-network network element, bandwidth resource information of theaccess-network network element, load information of the access-networknetwork element, architecture resource information of the access-networknetwork element, and user information of the access-network networkelement.
 6. The method according to claim 4, wherein the aggregate QoSinformation of the N network slices to which the M terminals belongincludes one or more of the following parameters: an aggregatethroughput requirement of the N network slices to which the M terminalsbelong; a maximum throughput limit of the N network slices to which theM terminals belong; or a minimum throughput limit of the N networkslices to which the M terminals belong.
 7. An apparatus for networkslice configuration, applied to an access- network network element,comprising: at least one processor; and a non-transitory memory storinginstructions that, when executed by the at least one processor, causethe apparatus to perform operations comprising: receiving network sliceconfiguration information from a first network device, wherein: thenetwork slice configuration information comprises network slice servicemanagement information, wherein the network slice service managementinformation comprises aggregate quality of service (QoS) information ofN network slices to which M terminals belong, and wherein M is a naturalnumber and N is a natural number; and performing network sliceconfiguration based on the network slice configuration information. 8.The apparatus according to claim 7, wherein the operations comprise:sending capability information of the access-network network element tothe first network device, wherein the first network device determinesthe network slice configuration information based on the capabilityinformation of the access-network network element, and wherein thecapability information of the access-network network element comprisesone or more of identification information of the access-network networkelement, version information of the access-network network element,antenna resource information of the access-network network element,bandwidth resource information of the access-network network element,load information of the access-network network element, architectureresource information of the access-network network element, and userinformation of the access-network network element.
 9. The apparatusaccording to claim 7, wherein the aggregate QoS information of the Nnetwork slices to which the M terminals belong includes one or more ofthe following parameters: an aggregate throughput requirement of the Nnetwork slices to which the M terminals belong; a maximum throughputlimit of the N network slices to which the M terminals belong; or aminimum throughput limit of the N network slices to which the Mterminals belong.
 10. An apparatus for network slice configuration,applied to a first network device, comprising: at least one processor;and a non-transitory memory storing instructions that, when executed bythe at least one processor, cause the apparatus to perform operationscomprising: sending network slice configuration information to anaccess-network network element, wherein: the network slice configurationinformation comprises network slice service management information,wherein the network slice service management information comprisesaggregate quality of service (QoS) information of N network slices towhich M terminals belong, and wherein M is a natural number and N is anatural number.
 11. The apparatus according to claim 10, wherein theoperations comprise: receiving capability information of theaccess-network network element from the access-network network element;and determining the network slice configuration information based on thecapability information of the access-network network element, whereinthe capability information of the access-network network elementcomprises one or more of identification information of theaccess-network network element, version information of theaccess-network network element, antenna resource information of theaccess-network network element, bandwidth resource information of theaccess-network network element, load information of the access-networknetwork element, architecture resource information of the access-networknetwork element, and user information of the access-network networkelement.
 12. The apparatus according to claim 10, wherein the aggregateQoS information of the N network slices to which the M terminals belongincludes one or more of the following parameters: an aggregatethroughput requirement of the N network slices to which the M terminalsbelong; a maximum throughput limit of the N network slices to which theM terminals belong; or a minimum throughput limit of the N networkslices to which the M terminals belong.